Skip to content

Update github actions (main) (minor) - #235

Merged
robnester-rh merged 1 commit into
mainfrom
renovate/main-github-actions
Sep 4, 2026
Merged

Update github actions (main) (minor)#235
robnester-rh merged 1 commit into
mainfrom
renovate/main-github-actions

Conversation

@renovate

@renovate renovate Bot commented Mar 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
actions/checkout action minor v6.0.3 → v6.1.0
conforma/.fullsend workflow pinDigest → 4ad3612
conforma/github-workflows workflow pinDigest → eb2bb49
conforma/pr-size-label-action action minor v1.0.0 → v1.2.0
github/codeql-action action minor v4.32.6 → v4.37.9
step-security/harden-runner action minor v2.15.1 → v2.21.1

Release Notes

actions/checkout (actions/checkout)

v6.1.0

Compare Source

conforma/pr-size-label-action (conforma/pr-size-label-action)

v1.2.0

Compare Source

What's Changed

Full Changelog: conforma/pr-size-label-action@v1...v1.2.0

v1.1.0

Compare Source

Highlights

  • Node.js 24 runtime — upgraded from Node.js 20 ahead of the GitHub Actions deprecation deadline
  • @actions/core v2 — updated from v1
  • Apache-2.0 license — corrected in package.json
  • Separated entrypoint from logic — src/main.js entrypoint, src/index.js exports run() for testability
  • Non-PR event guard — fails fast with a clear message if triggered on a non-PR event
  • Tightened label filter — matches size: prefix (with trailing space) to avoid collisions
  • 23 unit tests — comprehensive Jest test suite added
  • Node.js version pinning — .nvmrc and engines field added
  • npm audit fixes — resolved known vulnerabilities in dependencies

What's Changed

What's Changed

New Contributors

Full Changelog: conforma/pr-size-label-action@v1.0.0...v1.1.0

github/codeql-action (github/codeql-action)

v4.37.9

Compare Source

v4.37.8

Compare Source

No user facing changes.

v4.37.7

Compare Source

v4.37.6

Compare Source

  • Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #​4070

v4.37.5

Compare Source

  • Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #​4061

v4.37.4

Compare Source

v4.37.3

Compare Source

No user facing changes.

v4.37.2

Compare Source

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #​4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #​4007

v4.37.1

Compare Source

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #​3956
  • Update default CodeQL bundle version to 2.26.1. #​4019

v4.37.0

Compare Source

  • Update default CodeQL bundle version to 2.26.0. #​3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #​3973

v4.36.3

Compare Source

No user facing changes.

v4.36.2

Compare Source

  • Cache CodeQL CLI version information across Actions steps. #​3943
  • Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #​3937
  • Update default CodeQL bundle version to 2.25.6. #​3948

v4.36.1

Compare Source

No user facing changes.

v4.36.0

Compare Source

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #​3894
  • Add support for SHA-256 Git object IDs. #​3893
  • Update default CodeQL bundle version to 2.25.5. #​3926

v4.35.5

Compare Source

  • We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #​3899
  • For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #​3791
  • If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #​3892
  • Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #​3880

v4.35.4

Compare Source

v4.35.3

Compare Source

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #​3837
  • Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #​3850
  • Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #​3853
  • Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #​3852
  • Update default CodeQL bundle version to 2.25.3. #​3865

v4.35.2

Compare Source

  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #​3795
  • The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #​3789
  • Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #​3794
  • Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #​3807
  • Update default CodeQL bundle version to 2.25.2. #​3823

v4.35.1

Compare Source

v4.35.0

Compare Source

v4.34.1

Compare Source

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #​3762

v4.34.0

Compare Source

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #​3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #​3584
  • Update default CodeQL bundle version to 2.25.0. #​3585

v4.33.0

Compare Source

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #​3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.

  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #​3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #​3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #​3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #​3564

  • A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #​3570

step-security/harden-runner (step-security/harden-runner)

v2.21.1

Compare Source

What's Changed
  • Improved performance of the disable-sudo feature.
  • Fixed an issue in the Community tier where new endpoints required by the GitHub Actions runner were not being implicitly allowed in block mode.
  • Fixed the Harden-Runner post step failing on Linux distributions that do not have a merged /usr filesystem layout (for example Debian 11), where /usr/bin/echo does not exist. This mainly affected self-hosted runners.
  • Documentation updates: clarified which features are in the Community (free) vs Enterprise tier.

Full Changelog: step-security/harden-runner@v2.21.0...v2.21.1

v2.21.0

Compare Source

What's Changed
  • Support for denied endpoints in block mode. This is included in the enterprise tier. Customers can deny outbound calls, for example, to public package registries.
  • Improved Support for AWS CodeBuild GitHub Actions Runners.
  • Bug fixes.

Full Changelog: step-security/harden-runner@v2.20.1...v2.21.0

v2.20.1

Compare Source

What's Changed
  • AWS CodeBuild-hosted runner support
  • Implicitly allow single-labeled (internal) domains in block-mode

Full Changelog: step-security/harden-runner@v2.20.0...v2.20.1

v2.20.0

Compare Source

What's Changed
  • Support for block policy for MacOS and Windows GitHub-hosted runners
  • Support for Bitrise MacOS GitHub Actions runners
  • HTTPS monitoring support for Bun for Linux runners (enterprise tier)

Full Changelog: step-security/harden-runner@v2.19.4...v2.20.0

v2.19.4

Compare Source

What's Changed
  • Improvements for HTTPS Monitoring for the Enterprise tier of Harden Runner

Full Changelog: step-security/harden-runner@v2.19.3...v2.19.4

v2.19.3

Compare Source

What's Changed

Full Changelog: step-security/harden-runner@v2.19.2...v2.19.3

v2.19.2

Compare Source

What's Changed
  • Update the Harden Runner agent for enterprise tier to use go 1.26 and fix minor bugs.

Full Changelog: step-security/harden-runner@v2.19.1...v2.19.2

v2.19.1

Compare Source

What's Changed

What the fix changes

  • Harden-Runner will detect ubuntu-slim runners and exit cleanly with an informational log message, instead of post harden runner step failing on chown: invalid user: 'undefined'.

What the fix does not do

  • Jobs running on ubuntu-slim will not be monitored by Harden-Runner. The agent relies on kernel-level features (that require elevated capabilities).
  • Per GitHub's docs on single-CPU runners: "The container for ubuntu-slim runners runs in unprivileged mode. This means that some operations requiring elevated privileges such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features are not supported." Those low-level kernel features are what the agent needs, so monitoring inside the unprivileged container is not feasible today.

For StepSecurity enterprise customers
If your security posture requires that workflows are always monitored, you can block the use of ubuntu-slim via workflow run policies see the Runner Label Policy docs. This lets you enforce that jobs only run on monitored runner types.

New Contributors

Full Changelog: step-security/harden-runner@v2.19.0...v2.19.1

v2.19.0

Compare Source

What's Changed
New Runner Support

Harden-Runner now supports Depot, Blacksmith, Namespace, and WarpBuild runners with the same egress monitoring, runtime monitoring, and policy enforcement available on GitHub-hosted runners.

Automated Incident Response for Supply Chain Attacks
  • Global block list: Outbound connections to known malicious domains and IPs are now blocked even in audit mode.
  • System-defined detection rules: Harden-Runner will trigger lockdown mode when a high risk event is detected during an active supply chain attack (for example, a process reading the memory of the runner worker process, a common technique for stealing GitHub Actions secrets).
Bug Fixes

Windows and macOS: stability and reliability fixes

Full Changelog: step-security/harden-runner@v2.18.0...v2.19.0

v2.18.0

Compare Source

What's Changed

Global Block List: During supply chain incidents like the recent axios and trivy compromises, StepSecurity will add known malicious domains and IP addresses (IOCs) to a global block list. These will be automatically blocked, even in audit mode, providing immediate protection without requiring any workflow changes.

Deploy on Self-Hosted VM: Added deploy-on-self-hosted-vm input that allows the Harden Runner agent to be installed directly on ephemeral self-hosted Linux runner VMs at workflow runtime. This is intended as an alternative when baking the agent into the VM image is not possible.

Full Changelog: step-security/harden-runner@v2.17.0...v2.18.0

v2.17.0

Compare Source

What's Changed
Policy Store Support

Added use-policy-store and api-key inputs to fetch security policies directly from the StepSecurity Policy Store. Policies can be defined and attached at the workflow, repo, org, or cluster (ARC) level, with the most granular policy taking precedence. This is the preferred method over the existing policy input which requires id-token: write permission. If no policy is found in the store, the action defaults to audit mode.

Full Changelog: step-security/harden-runner@v2.16.1...v2.17.0

v2.16.1

Compare Source

What's Changed

Enterprise tier: Added support for direct IP addresses in the allow list
Community tier: Migrated Harden Runner telemetry to a new endpoint

Full Changelog: step-security/harden-runner@v2.16.0...v2.16.1

v2.16.0

Compare Source

What's Changed
  • Updated action.yml to use node24
  • Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS over HTTPS (DoH) by proxying DNS queries through a permitted resolver, allowing data exfiltration even with a restrictive allowed-endpoints list. This issue only affects the Community Tier; the Enterprise Tier is not affected. See GHSA-46g3-37rh-v698 for details.
  • Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS queries over TCP to external resolvers, allowing outbound network communication that evades configured network restrictions. This issue only affects the Community Tier; the Enterprise Tier is not affected. See GHSA-g699-3x6g-wm3g for details.

Full Changelog: step-security/harden-runner@v2.15.1...v2.16.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 2 times, most recently from 3a6bc21 to d4754e4 Compare March 20, 2026 22:00
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from c16a2fe to df40898 Compare March 31, 2026 15:01
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from a1c549e to 49fa7bd Compare April 10, 2026 20:44
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from 19329d4 to 91a5180 Compare April 20, 2026 09:35
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from 477f208 to ecc7ec1 Compare May 7, 2026 21:25
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from c95ed4b to e83fa17 Compare May 15, 2026 13:54
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 2 times, most recently from 0a828a5 to fb8ef67 Compare May 22, 2026 12:59
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 2 times, most recently from 37414f4 to 5d4be37 Compare June 4, 2026 19:12
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch 3 times, most recently from d62abcf to 4a5a23c Compare July 8, 2026 12:57
@renovate
renovate Bot force-pushed the renovate/main-github-actions branch from 4a5a23c to a5350f2 Compare July 12, 2026 10:14
fullsend-ai-review[bot]

This comment was marked as outdated.

Sign in to view

@renovate
renovate Bot force-pushed the renovate/main-github-actions branch from 64dcadb to 0143a1b Compare August 31, 2026 02:06
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:07 AM UTC · Completed 2:16 AM UTC

Commit: 87c4a29 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.72

fullsend-ai-review[bot]

This comment was marked as outdated.

Sign in to view

@renovate
renovate Bot force-pushed the renovate/main-github-actions branch from 0143a1b to e91c4a5 Compare September 1, 2026 19:04
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 1, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:06 PM UTC · Completed 7:16 PM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.47

fullsend-ai-review[bot]

This comment was marked as outdated.

Sign in to view

@renovate
renovate Bot force-pushed the renovate/main-github-actions branch from e91c4a5 to e8d03b6 Compare September 3, 2026 16:49
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:50 PM UTC · Completed 5:08 PM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.30

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Sep 3, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown

Risk Assessment: moderate (2/5)

Details

Small Renovate bot PR touching only .github/workflows/ files (protected paths elevate Tier 1 despite the mechanical, config-only nature of the change; low churn and stable authorship keep the composite moderate).

Previous run

Risk Assessment: moderate (2/5)

Details

Routine dependency updates in well-maintained GitHub Actions workflows; low risk with active bot-driven maintenance and no security-sensitive changes, but protected-path signal keeps the composite in the moderate range.

Previous run (2)

Risk Assessment: moderate (2/5)

Details

Bot-authored Renovate PR making purely mechanical minor-version and pinned-SHA bumps in five stable, low-churn CI workflow files with no production code, tests, or dependency manifests touched.

Previous run (3)

Risk Assessment: moderate (2/5)

Details

Bot-authored (Renovate) XS-sized GitHub Actions version bump across 5 CI workflow files with only 14 lines changed; protected paths and CI-change flags elevate Tier 1 but bot authorship, zero security sensitivity, and stable low-churn file history keep overall risk moderate.

fullsend-ai-review[bot]

This comment was marked as outdated.

Sign in to view

@renovate
renovate Bot force-pushed the renovate/main-github-actions branch from e8d03b6 to eab8058 Compare September 4, 2026 01:43
@renovate
renovate Bot requested a review from a team as a code owner September 4, 2026 01:43
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 1:44 AM UTC · Completed 1:51 AM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.03

@fullsend-ai-review
fullsend-ai-review Bot dismissed stale reviews from themself September 4, 2026 01:51

Superseded by updated review

@fullsend-ai-review

fullsend-ai-review Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:44 PM UTC · Completed 2:53 PM UTC

Commit: ca5794c · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.58

@fullsend-ai-review

fullsend-ai-review Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:09 PM UTC · Completed 5:16 PM UTC

Commit: 4ad3612 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.95

@fullsend-ai-retro

fullsend-ai-retro Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 10:21 PM UTC · Completed 10:30 PM UTC

Commit: 4ad3612 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $3.17

@fullsend-ai-retro

fullsend-ai-retro Bot commented Sep 4, 2026

Copy link
Copy Markdown

Retro on conforma/user-guide#235

Renovate PR (GitHub Actions minor/pinDigest updates across 5 workflow files in .github/workflows/) opened 2026-03-17, merged 2026-09-04. The fullsend-ai-review agent ran 19 times on this PR, the last ~5 of which each cost ~$1.61–$3.30 (Opus). The finding was substantively unchanged every time: [protected-path] .github/ — a mechanical, bot-authored, renovate.json-authorized version bump that policy still requires a human to sign off on. Severity oscillated (High → Medium → Low → info-only) across runs on essentially the same diff. Human robnester-rh approved (no review comments) and merged.

What the trace actually shows

  • Every re-review was triggered by pull_request_target/synchronize from Renovate rebasing when main moved. No /fs-review commands, no schedule, no manual re-runs.
  • The Commit: <sha> line in the status comment (e.g. Commit: 87c4a29 on 15 comments in a row) is not the reviewed PR head SHA — it is github.sha from the .fullsend dispatch context (the pinned .fullsend@main deploy SHA). The actual PR head changed on every rebase (a5350f2 → d67b1a6 → ... → 95aaeb7), so this was not literal same-SHA re-review — but it was same-content re-review, which is the same waste with an extra confounder for retro analysis.
  • The final review (33898933069) hit claude-sonnet-4-5@20250929 is not available on your vertex deployment on three Sonnet-tier sub-agents (risk-assessment, intent-coherence, style-conventions) and retried on Haiku; challenger pass was skipped as a result.

Filed nothing new — every improvement is already tracked

Every angle I would have proposed is already an open issue. Rather than duplicate, filing this evidence here:

Renovate rebase re-review churn (root cause of the 19 runs):

  • fullsend-ai/fullsend#4652 — Skip re-reviews when Renovate rebases without changing the diff. New evidence: 19 near-identical reviews on this one PR, ~$30–50+ in the last ~15 alone.
  • fullsend-ai/fullsend#4596 — Avoid full re-reviews on content-identical Renovate rebases. Same evidence applies.
  • fullsend-ai/fullsend#6278 — Set Renovate rebaseWhen: conflicted to reduce spurious dispatches. Directly addresses the trigger side; would have collapsed 19 runs to ~1.
  • fullsend-ai/agents#323 — Pre-review guard should short-circuit when the SHA already has a successful review. New evidence: no such guard exists today — scripts/pre-fetch-prior-review.sh only extracts PRIOR_REVIEW_SHA for anchoring, never compares/exits.

Bot-PR fast-path / protected-path carveout (would have avoided most of the 19 runs entirely):

Cost efficiency on mechanical diffs:

Vertex model availability (hit on the final run):

Misleading Commit: <sha> in status comment:

  • fullsend-ai/fullsend#5378 — github.sha wrong for pull_request_target; root cause is COMMIT_SHA: ${{ github.sha }} in action.yml. New evidence: in the reusable-dispatch-from-.fullsend path, the fallback lands on the deploy pin (87c4a29) rather than the PR head, so 15 status comments in a row all displayed the same SHA even though the reviewed head differed on each — a confounder for retro analysis and for humans skimming the PR timeline.
  • fullsend-ai/fullsend#3873 — Same class (base-vs-head SHA in status comment).

What went well

  • Later reviews correctly recognized the SHA-pin conversions (@main → SHA on conforma/.fullsend/.github/workflows/dispatch.yml and conforma/github-workflows) as supply-chain improvements and downgraded severity accordingly.
  • The prior-review anchoring context (PRIOR_REVIEW_PROVENANCE) was correctly reported when unverifiable.
  • Human approval (no comments) is consistent with a maintainer confirming the routine bot-authored update — treat this as a real review, not a rubber stamp.

No new proposals filed — the outstanding-issue set already covers every action item this retro would recommend.

@fullsend-ai-retro fullsend-ai-retro Bot mentioned this pull request Sep 9, 2026
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@robnester-rh robnester-rh robnester-rh approved these changes
+1 more reviewer
@fullsend-ai-review fullsend-ai-review[bot] fullsend-ai-review[bot] left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

github_actions Pull requests that update GitHub Actions code main renovate requires-manual-review Review requires human judgment risk/moderate PR risk: moderate size: XS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@robnester-rh